I have the following template for the issues, I would like to do that when for example the second field Additional context is empty, then the user does not put any text.
When the issues is created, instead of writing me "No response", I would like the Additional context field not to be put.
Can you tell me if it can be done?
name: 🐛 Bug Report
description: Create a report to help us improve
title: "🐛 [BUG] - YOUR_DESCRIPTION"
labels: [🐛 bug]
body:
- type: textarea
attributes:
label: Describe the bug
placeholder: A clear and concise description of what the bug is.
- type: textarea
attributes:
label: Additional context
placeholder: Add any other context about the problem here.
I'm using Kotlin and AWS Amplify to make a simple mobile app. I'll begin by showing what I have setup. My schema.graphql:
type OfferGQL #model {
id: ID!
name: String!
description: String!
address: String!
price: Float!
}
My AWS plugins are setup like this:
Amplify.addPlugin(AWSCognitoAuthPlugin())
Amplify.addPlugin(AWSS3StoragePlugin())
Amplify.addPlugin(AWSDataStorePlugin())
Amplify.configure(applicationContext)
This is how I try to save my data to the DataStore:
// Create a new offer object
val newOffer = OfferGQL.builder()
.name(textFieldOfferName.text.toString())
.description(textFieldOfferDescription.text.toString())
.address(textFieldOfferAddress.text.toString())
.price(textFieldOfferPrice.text.toString().toFloat())
.build()
// Put it in the DataStore
Amplify.DataStore.save(newOffer,
{result ->
runOnUiThread{Toast.makeText(this,"Offer added successfully", Toast.LENGTH_LONG).show()}
},
{error ->
println(error.message)
println(error.localizedMessage)
println(error.cause)
println(error.recoverySuggestion)
})
The problem is that when I invoke Amplify.DataStore.save() the entire app freezes. I followed the documentation to configure everything so I don't really now why this is happening.
After a full reinstall of the app on my phone the function finally works.
I am unable to delete any row in my interactive report.
Steps: Create new interactive report page.
Create page item P400_EMPLOYEE_ID referring to PK employee_id and set to hidden.
For the virtual column 'del', properties are:
Type: link
URL: javascript:void(null);
Link Text:
Link Attributes: data-id=#EMPLOYEE_ID#
Create Dynamic Action option:
Name: DA_DELETEROW
Event: Click
Selection Type: jQuery Selector
jQuery Selector: .delete-irrow
Event Scope: Dynamic
right-click on the Dynamic Action DA_DELETEROW and select Create True Action :
Action: Confirm
Text: Are you sure to delete this employee?
2nd true action:
Action: Set Value
Set Type: JavaScript Expression
JavaScript Expression: $(this.triggeringElement).parent().data('id')
Selection Type: Item(s)
Item(s): P400_EMPLOYEE_ID
3rd true action:
Action: Execute PL/SQL Code
PL/SQL Code: Delete from employee_leave where employee_id= :P400_EMPLOYEE_ID;
Items to Submit: P400_EMPLOYEE_ID
Last true action set as refresh the region.
Despite this, i can see the delete button but unable to delete any row.
It just refreshes the page on delete and no row is deleted from report or table.
Please help!!!!!!
Why are you trying to remove a row from the Interactive Grid using dynamic actions? Wouldn't it be simpler to delete the row from the database and refresh the Interactive Report?
For my custom Drupal 8 (8.7.8) module, I have the following ...
my_module.reports:
route_name: my_module.reports
title: 'Reports'
base_route: my_module.dashboard
weight: 80
in my menu system in my_module.links.menu.yml and it appears as a tab on my dashboard I'm building. On that page, the route controller I have is...
_controller: '\Drupal\system\Controller\SystemController::systemAdminMenuBlockPage'
I'm hoping to make there a list of further links to reports. But this (from my_module.links.menu.yml) ...
my_module.reports.territories:
title: 'Territories'
description: '...'
route_name: my_module.reports.territories
parent: my_module.reports
weight: 10
Doesn't show up. All I get when I go to that page is:
"You do not have any administrative items."
What am I missing? Is it somehow not possible to make children of tasks in this way or is this something else?
Thanks!
Finally worked it out. I had to ALSO add ...
my_module.reports:
title: 'Reports'
parent: system.admin_config
route_name: my_module.reports
... to my_module.links.menu.yml. I could then leave the link in my_module.links.task.yml as well to create the final thing I wanted.
I have a PWA built with ionic deep linker. I have done a demo here https://stackblitz.com/edit/ionic-mee2ut?file=app%2Fcustomer%2Fcustomer.component.html where the browser back button doesn't work as expected.
Steps to reproduce
1.In Dashboard page click on edit button.It will navigate to customer
page(see URL.It is changed to /Customer/CustomerId).
2.In Customer page, you will see the customer info and other customers
list, there click edit from other customers list.This will open another
page.(see URL.It is changed to /Customer/CustomerId).
3.Click on browser back button u can see that the URL is changed but the
view is not updated.
If I repeat steps 1 & 2 then click on nav back button instead of browser button then it works correctly.Both the URL and the view gets updated.
Is there something I am doing wrong because the browser back button does not work as expected or this is issue of ionic framework.
This is how i navigate between views
EditCustomer(Customer: any) {
this.navCtrl.push('Customer', { Id: Customer.Id, Name: Customer.Name });
}
Can somebody please tell me a way how to resolve this issue?
I saw your code in the above url, you are passing id as param but not the name so, that is the reason url is changing but data is not reflected i modified your code in app.module.ts file please replace this code in your app.module.ts file
IonicModule.forRoot(MyApp, {}, {
links: [
{ component: DashboardComponent, name: 'Dashboard', segment: 'Dashboard' },
{ component: CustomerComponent, name: 'Customer', segment: 'Customer/:Id/:Name' }
]
})
Please replace your app.module.ts with the following code
import { Component } from '#angular/core';
import { Platform, IonicApp, App } from 'ionic-angular';
#Component({
templateUrl: 'app.html'
})
export class MyApp {
rootPage:any = 'Dashboard';
constructor(private _app: App, platform: Platform, private _ionicApp: IonicApp,) {
platform.ready().then(() => {
this.setupBackButtonBehavior();
});
}
private setupBackButtonBehavior () {
// If on web version (browser)
if (window.location.protocol !== "file:") {
// Register browser back button action(s)
window.onpopstate = (evt) => {
//Navigate back
if (this._app.getRootNav().canGoBack())
this._app.getRootNav().pop();
};
}
}
}
I was able to use something like this:
let randomID = this.makeId(5); // random string id
this.navCtrl.push('path', {
eventID: eventID,
instituteID: instituteID,
randomID: randomID
}, {
id: `path/${eventID}/${instituteID}/${randomID}`
});
This "id" seems to fix it, but if you can go to the same page, then it requires a "random" value to separate each visit to that page.
#IonicPage({
name: 'path',
segment: 'path/:instituteID/:eventID/:randomID'
})
It looks like, by default, it uses the name of the page as an id for that view. If multiple views have same id => issue when using browser back/forward. That's where the random comes in, to separate multiple instances of the same page.