Distinguish between PUT/POST requests

[butzist]

Description

Currently, when using this library with the Realtime Database, the set() function uses a POST request and thus inserts the provided data under a new key. Is this the intended behavior?
I would have expected to set the data at the provided path (without new sub-key), ie using PUT.

Example

#[derive(Debug, Default, Serialize, Deserialize)]
#[serde(default)]
struct SensorData {
    #[serde(rename = "t", skip_serializing_if = "Option::is_none")]
    temperature: Option<f32>,
    #[serde(rename = "h", skip_serializing_if = "Option::is_none")]
    humidity: Option<f32>,
    #[serde(rename = "d", skip_serializing_if = "Option::is_none")]
    dewpoint: Option<f32>,
}

let firebase = Firebase::new("https://xxx.firebasedatabase.app").unwrap();
let unix_time = start.duration_since(UNIX_EPOCH).unwrap().as_secs();
let data = SensorData {
    temperature: Some(42.0),
    ..Default::default()
};

firebase
    .at("weather")
    .at(&format!("{}", &unix_time))
    .set(&data)
    .await
    .expect("error writing to firebase");

Results in the following db entries:

Proposed changes

• Rename old set() to insert()
• Add new set() that uses PUT
• Fixes code formatting

[emreyalvac]

Hi,

Thanks for your time and work. Looks good!

I will release a new version soon for this improvement.

@butzist

[flejz]

This introduces a breaking change in the lib. I suggest leave set as the POST and create another put method that will do the PUT request.

[yoramboccia-IR]

Is anyone working on this PR?