Can anybody please explain how to pass reference strings for Delete actions of WorkspacePermission? I tried below,
`DeleteRequest delete = new DeleteRequest("/workspacepermission/9250166251u2788951014w1.js");
where
Workspacepermission id= 9250166251
User Object id= u2788951014
workspace number= w1`
Can anyone tell me how to pass them correctly?
Thanks!!
Sharat, nice work finding the issue with the pattern. I've chatted with the Rally developers and went ahead and opened an Issue for the Java RestApi out on the public Github repo:
https://github.com/RallyTools/RallyRestToolkitForJava/issues/5
You can track the resolution there - likely a new build of the jar coming fairly soon.
Related
I m trying to implement web push notification in my laravel application and I have setup web push for laravel by follow along the tutorial from the tutorial below
https://medium.com/#sagarmaheshwary31/push-notifications-with-laravel-and-webpush-446884265aaa
but there are still some question that I am not understand
Why we need the push_subscription in database ? It seems like I not even used it elsewhere ?
laravel notification not working ( if i did like this )
$users = User::whereIn('id', $vendor_user_ids)->get();
Notification::send($users, new WebChatPushNotification($chat));
but it work if I use Notification::send(User::all(), new WebChatPushNotification($chat));
since both of them are also a collection of user model, but why the latest one work.
and is there any other tutorial that can explain about web push more better that are recommended ?
Oh ya, for your information, I am using Laravel 8 and laravel-notification-channels/webpush package
Thanks in advance!
Finnally, I managed to solve it by myself.
the package itself will need to query the user's endpoint from the table when we try to notify the user.
Notification wont show because my $users is null, so nobody will be notify. such a silly mistakes, sorry for trying to ask such silly question here.
The problem I face is getting error in flutter plugin, and I have no solution. So I decide to edit some code in plugin, Am I right or wrong for that solution?
Any idea please ?
Thanks.
The answer is Yes.
Yes, you can fork that repo, edit the code according to your requirements.
And then, you have two options
1) Raise the Pull Request and wait till it gets merged or
2) Directly use your updated plugin code
Here is the reference link which will help you to use the updated plugin code as a dependancy.
Yes, definitely you can modify plugin as you want unless and until you can not solve errors without changing it.
I also once change rating plugin to get desire ui in my code.
I tried all sample and getting error - It is no longer necessary to append ".js" to WSAPI resources. Please Help with example.
That is just a warning- it's not actually preventing anything from working. Can you give us some more info on how you're accessing the api? Are you writing an app? Are you using one of the REST toolkits? Are there other errors in your response?
That warning just means you can drop the .js from all of the ref urls. The proper defect creation endpoint in wsapi version 2 is this:
/slm/webservice/v2.0/defect/create
I have been following these examples in a previous stack overflow example, I need to convert to an Integer id to an Azure mobile app, and need a MappingDomainManager class described by user Kiske1 in the post below.
Azure Mobile App using existing database
However, I have been unable to complete this as Automapper.impl.PropertyAccessor is “Type of namespace Impl does not exist…” I am using the latest Automapper dll v6.1.1.0.
Does anyone know where PropertyAccessor has been moved to/or replaced with?
Also, both examples that were specified in this post are from 2014, does anyone know of a more up to date walkthrough and preferably an example project?
Does anyone know where PropertyAccessor has been moved to/or replaced with?
I searched at AutoMapper project and found that PropertyAccessor has been removed. Also, I checked my mobile app project and the Automapper version is 3.3.1, the PropertyAccessor exists and the old sample could work. I assumed that you could try to downgrade the version of your Automapper to fix this issue.
does anyone know of a more up to date walkthrough and preferably an example project?
For Automapper 6.1.1, the usage for FindTypeMapFor method and the parameter type for GetExistingPropertyMapFor method have changed, you could modify your code under SimpleMappedEntityDomainManager as follows:
var m = Mapper.FindTypeMapFor<TModel, TData>();
m.GetExistingPropertyMapFor(new PropertyAccessor(typeof(TData).GetProperty("Id")));
To
var m = Mapper.Configuration.FindTypeMapFor<TModel, TData>();
m.GetExistingPropertyMapFor(typeof(TData).GetProperty("Id"));
Moreover, you could refer to adrian hall's book about The Domain Manager.
I've got a problem: I'm working on an external webinterface for my company and we use Atlassians JIRA as a project issue and tracking method. I am trying to connect our webinterface over the REST API. After a short research I found out, that Atlassian never implemented the possibility to create a new JIRA Project over their REST API. Well, that isn't that true, they've implemented it in the actual version (7.0) because they migrated their other two APIs to one REST API. Now comes my problem: We are currently unable to upgrade from version 6.4.4 to version 7.0.0. After a second search I found a workaround for this problem. You can find it here:
The real problem is that this workaround isn't working or I'm doing it wrong.
I've already tried it with a GET request and the given arguments as parameters and over the normal POST method with a JSON body in it.
What's my problem?
Here some more informations: When I try it over GET, I always receive the normal response for the URL (it returns a list with all available templates). When I try it over POST with a JSON body (this is by the way the normal method for the normal functions of the REST API) I get back a HTTP-Error 415 Unsupported media type.
it would be nice if someone could test this workaround with a 6.0+ version of JIRA
So after some months I got it by myself. You have to make a POST request with the following header fields:
Content-Type=application/x-www-form-urlencoded; charset=UTF-8
Authorization=Basic {set your credentials as a Base64-String: "user:password"}
X-Atlassian-Token=nocheck
Once done you can set your POST-Parameters to the following:
name=Name of the Project
key=Key of the Project
lead=Leader of the Project
keyEdited=true (don't change it!)
projectTemplateWebItemKey=com.atlassian.jira-legacy-project-templates:jira-blank-item (don't change it!)
projectTemplateModuleKey=com.atlassian.jira-legacy-project-templates:jira-blank-item (don't change it!)
Hope that this helps someone, Jira is just weird in some cases :/