doodle | A Simple Java MVC Framework。提供Bean容器、Ioc、Aop、MVC功能 | Aspect Oriented library

As of Spring Boot 2.6, the property spring.mongodb.embedded.version must be set to use the auto-configured embedded MongoDB. It's mentioned in the release notes: https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.6-Release-Notes#embedded-mongo

This is also what the error message you posted, advises to do: Set the spring.mongodb.embedd ed.version property or define your own MongodConfig bean to use embedded MongoDB

The annotation @DataMongoTest is meta-annotated with @ImportAutoConfiguration and @AutoConfigureDataMongo, and is designed to trigger auto-configuration of MongoDB unless explicitly disabled as you do in the working configuration examples.

In your first configuration example, the annotation @EnableAutoConfiguration(exclude = EmbeddedMongoAutoConfiguration.class) does not override this effect of @DataMongoTest.

With Spring Boot 2.5.6, the auto-configured MongodConfig bean is most likely also part of the application context but not effectively used. But this depends on the rest of the code and in particular on the MongodbContainerInitializer.

You need to make sure your code is written inside a Future function like so:

The alignment property of Container is applicable to the child inside that container. For your specific requirement, you can set the mainAxisAlignment of your Column to Space Between:

A few things:

First, you have a problem with namespaces and Deprecated XLink URL reference attributes.

Second, in

try this Evaluate when the counter is equal to the size of your array if so then do the job you want

I'm always happy to see newcomers devoting time to study. First of all, good job! Unfortunately I'm not a very good teacher, but I put together a little example of this slider you're working on. You can check it clicking here.

Basically what is going on is:

1. The HTML is divided into two sections: the slider & the navbar.
2. I hide all slides by default applying a display: none to them. They're only visible when I add an additional class.
3. Detect the hover method via javascript. Whenever the navbar item is hovered on, you will detect its position (I added a data attribute called data-position to find out which position it is) and show the correspondent slider.

So, if the navbar has the data-position of 2, I know that I must show the second slide. To do that, I use .slider .slider-item:nth-child(2).

As I mentioned I'm not the best at explaining, but I hope this helps you out a little bit. Keep studying and don't give up!

HTML:

Query

• its an aggregation update even if pipeline doesn't allow us to use stages like group lookup etc that here is used. (you can use $out and replace collection after or $merge to replace documents(similar to update))

• first map

  • for each trait(document member of traits), it makes it into array
    [["trait_type": "type"] ["value": "Male"] ["display_type": null] ...]
  • reduce on that array to contruct from them 1 document only
    {"type" "type","value" :"Male"} (does also that lowercase and "_")

• Now traits its like

Saving data on keys, makes it more complicated, because we have to do things like $objectToArray see this also

For each trait in traits array adds 1 field to the eternal document. {"trait_$value" : ["$value1" "$value2"]} if trait had many values of {"trait_$value" : "$value1"} if trait had 1 value only

("trait_$value" gets lower-case and replace spaces with "_" also)

Query (works on your data and produce results with data on keys)

If you look at the code example we have 2 collections, your collection, and one dummy c2=[{}], we need this to make the $lookup so we can use the stage operator like $group dont delete it, just add this dummy 1 empty document collection to the database.

Because we had to do things like $group it was not possible to do it with update, there are 2 solutions

• add an $out stage to the aggregation (output to new collection and replace it)
• add a $merge stage to the aggregation, that works like an update

Example data1 Test code here

Example data2 (i added 1 eye_color to make an array) Test code here

Query

• $lookup with a dummy collection [{}] reason to do that is to use stage operators inside 1 document to avoid things like unwind-group (we need to group that traits array)
• Inside the lookup pipeline (in the pipeline its just the ROOT doc)
• unwind traits (each traite separate document)
• group by trait_type, collect the values {"_id" : type1 "values" [value1 ...]} {"_id" : type2 "values" [value1 ...]}
• now on that we change {"_id" : type1 "values" [value1 ...]} to (object to array $$ROOT) [["traits_type1" [value1 ...]]] (if 1 value we dont have array) to (array to object $$pair) {"traits_type1" : [value1 ...]}
• the next is making that array "traits" output of lookup to object
• and add it back to the root

You can add a modifier to the hero component. In your case, it can be done as follows,