Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Aug 13 06:40

    atooni on 3.6.1

    (compare)

  • Aug 13 05:59

    atooni on 3.6

    (compare)

  • Aug 13 05:53

    atooni on main

    Remove obsolete files (compare)

  • Aug 04 14:54

    atooni on 3.6-RC5

    (compare)

  • Aug 04 14:53

    atooni on main

    Ensure send timeout to send wir… (compare)

  • Jul 31 14:10

    atooni on 3.6-RC4

    (compare)

  • Jul 31 14:10

    atooni on main

    bump blended-mill-version (compare)

  • Jul 31 12:38

    atooni on 3.6-RC3

    (compare)

  • Jul 31 11:58

    atooni on main

    Refactor REST JMS to allow wire… Refactor REST JMS to allow wire… (compare)

  • Jul 31 11:56

    atooni on awss3

    Refactor REST JMS to allow wire… Refactor REST JMS to allow wire… (compare)

  • Jul 28 12:40

    atooni on awss3

    Bump blended mill version, remo… Merge remote-tracking branch 'o… (compare)

  • Jul 26 10:40

    atooni on 3.6-RC2

    (compare)

  • Jul 26 10:40

    atooni on main

    externalise S3 access credentia… Final touches for 3.6-RC2 Merge remote-tracking branch 'o… (compare)

  • Jul 26 10:39

    atooni on awss3

    Final touches for 3.6-RC2 (compare)

  • Jul 26 09:57

    atooni on main

    Bump blended mill version, remo… (compare)

  • Jul 26 09:57

    atooni on 3.6-RC1

    Bump blended mill version, remo… (compare)

  • Jul 26 09:38

    atooni on main

    Merging aws changes Remove obsolete components move files and 7 more (compare)

  • Jul 24 09:40

    atooni on awss3

    externalise S3 access credentia… (compare)

  • Jul 23 18:30

    atooni on awss3

    Do not start S3 API bundle, rem… (compare)

  • Jul 23 18:10

    atooni on awss3

    Add aws API bundle (compare)

Andreas Gies
@atooni
For now you can take a look at the structure of the sample app and the components, especially the table and the tree
For starters, I would like to add a "sort" to the React Table, so that when you click on the header of one column the sort changes from NotSorted -> Ascending -> Descending -> Ascending -> Descending etc. Clicking on the header of another column should switch the sort order to that column
It might be an interesting task for you to think about how to implement this. Hint: You will need "state" on the level of the table component to keep track of the "current sorting state", which is to be modified whenever you click on one of the column headers
secondly you will need to introduce a "sort function" which sorts the individual rows of the table in the desired order.
Andreas Gies
@atooni
You can test and play with the changed table in the SampleApp
Of course, you will need to visualize the sorting state with a small icon next to the column header
Juanba98
@Juanba98
so i have to setup the sampleApp too?
Juanba98
@Juanba98
i mean how can i run it? because if i use the index-dev.html i just obtain a empty window @atooni
Andreas Gies
@atooni
I am wondering if we want to include the scala binary version in our symbolic names. We did not before, but with changing the build to potentially support multiple scalaversion may be we should
A side effect is that all config files would change their name as well as it is per default ${bundleSymbolicName}.conf
Tobias Roeser
@lefou
Yes, we should. We decided against before to avoid potential conflicts downstream, but IMHO we should correct this now.
Andreas Gies
@atooni
ok
Tobias Roeser
@lefou
@atooni You added another activator to blended.akka.http. Can you provide some context for it? dc48df13d8241417ecd48eac1f5c05fc08e0976d
Andreas Gies
@atooni
Yes. This is in relation to our ui projects. The idea is that in an UI project we do have the ScalaJS code that makes up the UI. The build process then goes and does its magic to apply webpack and create an OSGi bundle, so that the resulting UI can be hosted in a blended container. Within that magic we generate code for an Activator that is based on the Activator you have seen. I have included it in the core and Akka HTTP API because it seemed a common use case to me
In other words, It is to simplify the code generate and remove the boilerplate code to host the UI from the UI projects themselves
Tobias Roeser
@lefou
What's strange is that the bundle now has two activators
But only one is it's activator. Maybe it's just the misleading name.
Or we could move this into some kind of support package
Andreas Gies
@atooni
Could Rename it to something like ...ActivatorBase or ActivatorSupport
This a class that will never be instantiated itself, just inherited from
could also make it abstract
just saw it is abstract
it kind of belongs into that bundle unless we move the entire blended related API .... I would opt for renaming to something not ending in "activator"
Andreas Gies
@atooni
@lefou Do you think we should keep the projects creating the container separate from the integration tests ? - I am thinking along the lines that the result of a container project build are published / updated docker images. Then the integration test project could simply be turned into a nightly build grabing the latest image(s) of the containers and execute. Would probably also make it easier to create a configuration matrix, create a container for each element and IT test it
Andreas Gies
@atooni
@lefou In your latest change you have deleted the RuntimeConfigBuilder which we used to package our containers. Could you point me to the replacement to save me some time digging through the changes ?
Andreas Gies
@atooni
Found it - dont worry
Tobias Roeser
@lefou
Renamed it to ProfileBuilder
I now renamed to default branch to main.
Andreas Gies
@atooni
ok
Andreas Gies
@atooni
I should have moved master to main in all blended projects now
I have also changed the container project to publish docker images with a tag upon a tag push and with the content of version.txt for SNAPSHOTS
Andreas Gies
@atooni
https://github.com/woq-blended/blended.container is now on 3.2-alpha1 with integration tests running on GH actions & autopublishing of docker images
Andreas Gies
@atooni
FYI: feature references in feature configs will now look like :
{
  name = "blended.features.akka.http.modules"
  version = "3.2-SNAPSHOT"
  features = [
    { url="mvn:de.wayofquality.blended:blended.features_2.13:3.2-SNAPSHOT"
      names = ["blended.features.akka.http.base","blended.features.spring"],
      version = "3.2-SNAPSHOT" }
  ]
  bundles = [
    { url="mvn:de.wayofquality.blended:blended.akka.http.proxy_2.13:3.2-SNAPSHOT" },
    { url="mvn:de.wayofquality.blended:blended.akka.http.restjms_2.13:3.2-SNAPSHOT" },
    { url="mvn:de.wayofquality.blended:blended.akka.http.jmsqueue_2.13:3.2-SNAPSHOT" }
  ]
}