neu | A vi-like text editor for terminal | Command Line Interface library

The dialog is empty when using "neu" because you create a new version of "selected" each time. The old data is reappearing on "edit" because the previous time failed the validation, but you immediately close the dialog. Then you use p:resetInput which resets back to the stored value. If the selectList value is empty, it means that what's coming from the data source does not match any values in the Enum select list that you provide.

I had a number of issues getting the sample to work... missing form, update= having bad references. But I think the main design issue is that you're not displaying any validation errors in the dialog - just closing the dialog window immediately. And, by the way, you should mostly be using action= on command buttons, not actionListener=. See here to understand why. All field validation will have passed before the action method gets executed.

I suggest the following amendments:

As mentioned in Client-side hook / Committing-Workflow Hooks, a prepare-commit-msg could be used in conjunction with a commit template to programmatically insert information.

Example: janniks/prepare-commit-msg which does get the branch name (using Ruby, but you can use any scripting language you want):

Can filter the 'neg' and 'pos' from the dictionary using Dictionary Comprehensions

A key issue here is with your useEffect(() => loadnewmessages()). This is causing you a major performance overhead.

useEffect is a hook that has 2 parameters:

1. a "callback" - a function that will be run whenever the conditions (see #2)are met
2. dependency condition - one of 3 values:
   1. null (or omitted entirely) - the callback is run EVERY TIME the component renders
   2. [] (the empty array) - the callback is run only once when the component is first "mounted"
   3. [var1, var2, .....] - the callback is run if, each time the component is renders, any of the vars in the array has a different value than the last time the component rendered

In your case, you are fetching data from Firestore EVERY SINGLE TIME that the component renders.

Worse - each time your component renders you are using an onSnapshot() call meaning that you are creating a NEW realtime listener for data changes from that query every single time your component renders. After 1 render, you'll have a single listener. After you component renders a second time, you'll have 2 realtime listeners - each running the exact same Firestore query and listening for changes coming from Firestore. After 3 renders, you have 3 realtime listeners ...

Worse again - your realtime listener(s) get data from Firestore and update state. Updating state causes your component to re-render. See previous paragraph(!!!)

I recommend you look at how React's useEffect should be used in conjunction with Firestore realtime listeners. In particular, how to subscribe & unsubscribe to the listeners. Look for the word "unsubscribe" in this article for an example of useEffect() with Firestore (the section entitled "Streaming data in real time from Firestore as a side effect")

Are you only running mvn azure-webapp:deploy?

Make sure you run mvn package first, or mvn package azure-webapp:deploy. Otherwise it will just re-deploy the same WAR file. Include the -Pproduction flag if you want to run it in production mode.

Edit:

I set up a project myself and could reproduce your issue. After running mvn azure-webapp:config again twice and updating both Application and Runtime, it seems to work.

This did two changes to the pom.xml, try these out:

1. Add war under in the azure-webapp-maven-plugin.
2. Change jre8 to TOMCAT 9.0.

If I use vaderSentiment instead of nltk.sentiment.vader it works for me

Sorting based on polarity

You can use kotlin filter to filter the list based on Name

you're doing apply on series, not on dataframe.